Repository navigation
v5.8.2 — Demo ready: --assert-env flag + offline demo kit - #96
Conversation
- agent diagnose --assert-env <hash>: protect a frozen box with its own tool. Exit 0 if the env fingerprint is unchanged, 3 if it drifted, 2 if undeterminable. Reads a fresh worker fingerprint, falls back to the last report when unreachable. Keyless. Closes the un-built half of Demo Gate condition 6 (the DISPATCH KEEP-list assertion mechanism). Live-verified: match exits 0, wrong hash exits 3 against the real box. - demo/: keyless offline seeder + five-beat runbook rehearsable with ComfyUI down, real captured output, beats tagged offline vs server-gated. - README: baseline-bootstrap line in the run-reports section. +6 tests. Full suite: 4821 passed, 2 skipped (zero regressions). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T5Uf4eyeqC9K9eZSesVLrp
|
Warning Review limit reached
Next review available in: 19 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Closes the last un-built demo item and ships the offline rehearsal kit. (Bundles the offline demo kit that was held on a brightline review — content clean, cleared to ship.)
Added
agent diagnose --assert-env <hash>— protect a frozen demo box with its own tool ("we use the tool to protect the demo of the tool"). Record the fingerprint at Thursday rehearsal, assert it Friday morning: exit 0 unchanged, 3 drifted, 2 undeterminable. Reads a fresh worker fingerprint, falls back to the last report when the worker is unreachable. Keyless. This closes the un-built half of Demo Gate condition 6 (a DISPATCH KEEP-list item).demo/) —seed_diagnosis_demo.pyreproduces the run-report store keyless (3 clean baselines + 1 OOM break; no ComfyUI, no API key);DIAGNOSIS_RUNBOOK.mdis the five-beat runbook rewritten to rehearse fully offline, each beat tagged offline-reproducible vs server-gated, with real captured output.Verified
--assert-envlive against the real box: match → 0, wrong hash → 3,--jsonclean.Demo Gate after this
Conditions 2–5 offline-certified; the beat-2 live timing table is demonstrable (bridge confirmed installed); condition 6's assertion is now one command. Only the genuinely frozen-box items remain: condition 1 (twice-through) and the backup video.
🤖 Generated with Claude Code
https://claude.ai/code/session_01T5Uf4eyeqC9K9eZSesVLrp